version bump change by akshaydeo · Pull Request #2299 · maximhq/bifrost

akshaydeo · 2026-03-26T07:36:47Z

Summary

This release includes significant bug fixes for streaming responses across multiple providers (Bedrock, Anthropic, Gemini) and introduces a new model denylist feature for provider keys. The changes address duplicate events, token capture issues, and various provider-specific streaming problems.

Changes

Model Denylisting: Added blacklisted_models field to provider keys for excluding specific models from routing and list-models responses
Streaming Fixes: Resolved duplicate content_block_stop events in Bedrock, fixed cache token capture across providers, and prevented duplicate text in Gemini streaming
OTEL Tracing: Fixed response capture for streaming calls in OpenTelemetry tracing
Provider-Specific Fixes: Corrected reasoning content handling in OpenAI/Bedrock, fixed Vertex embedding global region URLs, and improved HTTP/2 toggle behavior
Infrastructure Improvements: Added broken pipe detection, moved gin migrations to Go to prevent deadlocks, and fixed WebSocket concurrent write safety
Configuration: Kept logging enabled by default and improved store parameter handling

Type of change

Affected areas

How to test

Validate streaming responses across different providers and test the new model denylist functionality:

# Core/Transports
go version
go test ./...

# Test streaming with various providers
curl -X POST /v1/chat/completions \
  -H "Content-Type: application/json" \
  -d '{"model": "gpt-4", "messages": [{"role": "user", "content": "Hello"}], "stream": true}'

# Test model denylisting
curl -X GET /v1/models \
  -H "Authorization: Bearer <key-with-blacklisted-models>"

Test the blacklisted_models configuration in provider keys to ensure excluded models don't appear in routing or list-models responses.

Screenshots/Recordings

N/A - Backend changes only

Breaking changes

Yes
No

Related issues

Addresses multiple streaming response issues and implements model filtering capabilities for better provider key management.

Security considerations

The model denylist feature enhances security by allowing fine-grained control over which models are accessible through specific provider keys.

Checklist

I read docs/contributing/README.md and followed the guidelines
I added/updated tests where appropriate
I updated documentation where needed
I verified builds succeed (Go and UI)
I verified the CI pipeline passes locally if applicable

CLAassistant · 2026-03-26T07:36:55Z

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

coderabbitai · 2026-03-26T07:36:56Z

📝 Walkthrough

Summary by CodeRabbit

New Features
- Added blacklisted models denylist support with denylist precedence over allow lists
Bug Fixes
- Resolved streaming event duplication, response typing, cache token capture, broken-pipe detection, and tracing issues
- Fixed model slug resolution and parameter handling across multiple providers
- Improved WebSocket and connection safety
Chores
- Version updates across core, framework, and plugins; dependency upgrades

Walkthrough

This PR performs a coordinated release across multiple modules, incrementing version numbers (core to 1.4.14, framework to 1.2.33, plugins, and transports to 1.4.17) and updating changelogs documenting recent fixes, features, and dependency upgrades across the codebase.

Changes

Cohort / File(s)	Summary
Core Release `core/version`, `core/changelog.md`	Bumped core version to 1.4.14 and documented multiple fixes including Bedrock streaming events, OpenAI response typing, OTEL tracing, cache token capture, HTTP/2 toggle, and Gemini adjustments.
Framework Release `framework/version`, `framework/changelog.md`	Bumped framework version to 1.2.33 and logged fixes for OpenTelemetry streaming, cache token capture, blacklisted_models support, Codex store parameter, Gin migrations, and Replicate model slug resolution.
Governance Plugin `plugins/governance/version`, `plugins/governance/changelog.md`	Bumped governance plugin to 1.4.33 and added denylist filtering feature for blacklisted_models with Replicate slug resolution fix.
Logging Plugin `plugins/logging/version`, `plugins/logging/changelog.md`	Bumped logging plugin to 1.4.33 and documented cache token capture fix for streaming calls.
Maxim Plugin `plugins/maxim/version`, `plugins/maxim/changelog.md`	Bumped maxim plugin to 1.5.32 and updated changelog entry prefix from `[changelog]` to `chore` format.
Dependent Plugin Updates `plugins/jsonparser/...`, `plugins/litellmcompat/...`, `plugins/mocker/...`, `plugins/otel/...`, `plugins/semanticcache/...`, `plugins/telemetry/...`	Updated versions and changelogs across six plugins documenting dependency upgrades to core v1.4.14 and framework v1.2.33.
Transports Release `transports/version`, `transports/changelog.md`	Bumped transports to 1.4.17 and restructured changelog with Features and Fixed sections documenting blacklisted_models denylist support, MCP gateway filtering, streaming event fixes, OTEL capture, connection pool error handling, and provider-level config persistence.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

danpiths
Pratham-Mishra04

Poem

🐰 Versions hop and changelogs bloom,
Across the plugins, clearing the room,
From core to transports, a synchronized dance,
Each module bumped in its release stance,
Fixes compiled, features in sight—
A coordinated hop to get things just right! 🎉

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The linked issue `#123` requests Files API support for providers (OpenAI, Anthropic), but the PR changes only contain version bumps and changelog updates for streaming fixes and model denylisting—no Files API implementation is present.	Implement Files API support as described in issue `#123`, or remove the issue link if this PR is unrelated to file API requirements.
Title check	❓ Inconclusive	The PR title 'version bump change' is vague and generic; it does not convey meaningful information about what is being versioned or why versions are being bumped.	Use a more descriptive title that summarizes the release, such as 'Release v1.4.14: streaming fixes and model denylisting feature' or similar.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description check	✅ Passed	The PR description is comprehensive and covers most required template sections including summary, changes, type of change, affected areas, testing instructions, breaking changes, and security considerations.
Out of Scope Changes check	✅ Passed	The PR consists entirely of version bumps and changelog updates across multiple modules, which are aligned with releasing bug fixes and new features described in the PR description.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch 03-26-version_bump_change

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

akshaydeo · 2026-03-26T07:37:02Z

version bump change #2299 👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

github-actions · 2026-03-26T07:37:08Z

🧪 Test Suite Available

This PR can be tested by a repository admin.

Run tests for PR #2299

greptile-apps · 2026-03-26T07:39:08Z

Confidence Score: 5/5

Safe to merge — purely version and changelog files with no code changes.

All 24 changed files are either version files (single-line version strings) or changelog markdown files. No code logic, dependencies, or configuration is modified. The version increments are consistent and sequential across all components, and changelog entries are well-documented.

No files require special attention.

Important Files Changed

Filename	Overview
core/version	Version bumped from 1.4.13 to 1.4.14
core/changelog.md	Changelog updated with 12 new entries covering fixes and one feature; replaces previous 2-entry stub
framework/version	Version bumped from 1.2.32 to 1.2.33
framework/changelog.md	Populated previously empty changelog with 7 entries covering fixes and one feature
transports/version	Version bumped from 1.4.16 to 1.4.17
transports/changelog.md	Changelog reformatted into structured markdown with emoji sections; adds several entries not present in core/framework changelogs (WebSocket concurrent writes, persist store config)
plugins/governance/version	Version bumped from 1.4.32 to 1.4.33
plugins/governance/changelog.md	Populated previously empty changelog with feature and fix entries specific to the governance plugin
plugins/logging/changelog.md	Populated previously empty changelog with one fix entry specific to cache token capture
plugins/maxim/changelog.md	Fixed malformed entry prefix from "[changelog]:" to "- chore:" and added trailing newline

_{Reviews (1): Last reviewed commit: "version bump change" | Re-trigger Greptile}

coderabbitai

🧹 Nitpick comments (1)

plugins/maxim/changelog.md (1)
1-1: Changelog label improvement, but verify PR scope alignment.

The change from [changelog]: to chore: follows conventional commit style and is an improvement. The trailing newline is also good practice.

However, I notice:

The PR is linked to Issue #123 (Files API Support), but this changelog only mentions a dependency upgrade

Need stack context to understand if Files API changes are in another PR in the stack

Please clarify:

Is the Files API feature implementation in another PR in the Graphite stack?

Should this PR's description be updated to reflect that it's a version bump/dependency upgrade rather than Files API Support?
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@plugins/maxim/changelog.md` at line 1, The changelog entry in
plugins/maxim/changelog.md currently reads "chore: upgraded maxim-go dependency
to latest version" but the PR is linked to Issue `#123` (Files API Support);
confirm whether the Files API implementation lives in a different stacked PR
and, if so, update this PR's description to clearly state that it is only a
dependency/version bump (reference Issue `#123` and the commit message "chore:
upgraded maxim-go dependency to latest version"); if the Files API changes are
present here, expand the changelog and PR description to include the Files API
scope and correct issue linkage so the changelog aligns with the actual code
changes.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@plugins/maxim/changelog.md`:
- Line 1: The changelog entry in plugins/maxim/changelog.md currently reads
"chore: upgraded maxim-go dependency to latest version" but the PR is linked to
Issue `#123` (Files API Support); confirm whether the Files API implementation
lives in a different stacked PR and, if so, update this PR's description to
clearly state that it is only a dependency/version bump (reference Issue `#123`
and the commit message "chore: upgraded maxim-go dependency to latest version");
if the Files API changes are present here, expand the changelog and PR
description to include the Files API scope and correct issue linkage so the
changelog aligns with the actual code changes.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a6de28b2-e5f3-4336-8be5-adc60940c88b

📥 Commits

Reviewing files that changed from the base of the PR and between 74e85a1 and 6f9c200.

📒 Files selected for processing (24)

core/changelog.md
core/version
framework/changelog.md
framework/version
plugins/governance/changelog.md
plugins/governance/version
plugins/jsonparser/changelog.md
plugins/jsonparser/version
plugins/litellmcompat/changelog.md
plugins/litellmcompat/version
plugins/logging/changelog.md
plugins/logging/version
plugins/maxim/changelog.md
plugins/maxim/version
plugins/mocker/changelog.md
plugins/mocker/version
plugins/otel/changelog.md
plugins/otel/version
plugins/semanticcache/changelog.md
plugins/semanticcache/version
plugins/telemetry/changelog.md
plugins/telemetry/version
transports/changelog.md
transports/version

akshaydeo · 2026-03-26T08:08:00Z

Merge activity

Mar 26, 8:08 AM UTC: A user started a stack merge that includes this pull request via Graphite.
Mar 26, 8:08 AM UTC: @akshaydeo merged this pull request with Graphite.

version bump change

6f9c200

akshaydeo marked this pull request as ready for review March 26, 2026 07:37

coderabbitai Bot requested review from Pratham-Mishra04 and danpiths March 26, 2026 07:38

coderabbitai Bot reviewed Mar 26, 2026

View reviewed changes

coderabbitai Bot approved these changes Mar 26, 2026

View reviewed changes

akshaydeo merged commit 172325e into main Mar 26, 2026
12 of 13 checks passed

akshaydeo deleted the 03-26-version_bump_change branch March 26, 2026 08:08

This was referenced Mar 29, 2026

v1.4.17-release-cut #2368

Merged

v1.4.19 cut #2430

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

version bump change#2299

version bump change#2299
akshaydeo merged 1 commit intomainfrom
03-26-version_bump_change

akshaydeo commented Mar 26, 2026 •

edited

Loading

Uh oh!

CLAassistant commented Mar 26, 2026

Uh oh!

coderabbitai Bot commented Mar 26, 2026 •

edited

Loading

Summary by CodeRabbit

Walkthrough

Changes

Estimated code review effort

Suggested reviewers

Poem

❌ Failed checks (1 warning, 1 inconclusive)

Uh oh!

akshaydeo commented Mar 26, 2026

Uh oh!

github-actions Bot commented Mar 26, 2026

Uh oh!

greptile-apps Bot commented Mar 26, 2026

Uh oh!

coderabbitai Bot left a comment

Uh oh!

akshaydeo commented Mar 26, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

akshaydeo commented Mar 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Changes

Type of change

Affected areas

How to test

Screenshots/Recordings

Breaking changes

Related issues

Security considerations

Checklist

Uh oh!

CLAassistant commented Mar 26, 2026

Uh oh!

coderabbitai Bot commented Mar 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Walkthrough

Changes

Estimated code review effort

Suggested reviewers

Poem

❌ Failed checks (1 warning, 1 inconclusive)

Uh oh!

akshaydeo commented Mar 26, 2026

Uh oh!

github-actions Bot commented Mar 26, 2026

🧪 Test Suite Available

Uh oh!

greptile-apps Bot commented Mar 26, 2026

Confidence Score: 5/5

Important Files Changed

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

akshaydeo commented Mar 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Merge activity

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

akshaydeo commented Mar 26, 2026 •

edited

Loading

coderabbitai Bot commented Mar 26, 2026 •

edited

Loading

akshaydeo commented Mar 26, 2026 •

edited

Loading